<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<title>Build Types</title>
<link rel="stylesheet" href="../default_style.css">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="keywords" content="Eclipse Build Types">
<meta name="description" content="Eclipse Project Build Types">
<meta name="author" content="David Williams">
</head>
<body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b"
  alink="#ff0000">
  <table border="0" cellspacing="5" cellpadding="2" width="100%">
    <tr>
      <td align="left" valign="top" colspan="2" bgcolor="#0080c0"><b><font
          face="Arial,Helvetica" color="#ffffff">Eclipse Project
            Build Types</font></b></td>
    </tr>
    <tr>
      <td align="right" valign="top"><img
        src="../images/Adarrow.gif" border="0" height="16" width="16"
        alt=""></td>
      <td>
        <p>
          <b><font face="arial,helvetica,geneva" size="-1">Releases</font></b>
          <br><font size="-1" face="arial,helvetica,geneva">
          </font>Releases are builds that have been declared major releases by
          the development team - for example &quot;R1.0&quot;. Releases
          are the right builds for people who want to be on a stable,
          tested release, and don't need the latest greatest features
          and improvements. Release builds always have an &quot;R&quot;
          at the beginning of the name i.e. R1.0, R2.0 etc. Non-release
          <font size="-1" face="arial,helvetica,geneva"> builds
            are named according to the date of the build - for example
            20011027 is the build from Oct 27, 2001.</font><br>
        </p>
      </td>
    </tr>
    <tr>
      <td align="right" valign="top"><img
        src="../images/Adarrow.gif" border="0" height="16" width="16"
        alt=""></td>
      <td><b><font face="arial,helvetica,geneva" size="-1">Stable
            Builds</font></b> <br> <font size="-1"
        face="arial,helvetica,geneva"> Stable builds are
          integration builds that have been found to be stable enough
          for most people to use. They are promoted from integration
          build to stable build by the architecture team after they have
          been used for a few days and deemed reasonably stable. The
          latest stable build is the right build for people who want to
          stay up to date with what is going on in the latest
          development stream, and don't mind putting up with a few
          problems n in order to get the latest greatest features and
          bug fixes. The latest stable build is the one the development
          team likes people to be using, because of the valuable and
          timely feedback. </font></td>
    </tr>
    <tr>
      <td align="right" valign="top"><img
        src="../images/Adarrow.gif" border="0" height="16" width="16"
        alt=""></td>
      <td>
        <p>
          <b><font face="arial,helvetica,geneva" size="-1">Integration
              Builds</font></b> <br> <font size="-1"
            face="arial,helvetica,geneva"> Periodically,
            component teams version off their work in what they believe
            is a stable, consistent state, and they update the build
            configuration to indicate that the next integration build
            should take this version of the component. Integration
            builds are built from these stable component versions that
            have been specified by each component team as the best
            version available. Integration builds may be promoted to
            stable builds after a few days of testing. Integration
            builds are built whenever new stable component versions are
            released into the build.</font>
        </p>
      </td>
    </tr>
    <tr>
      <td align="right" valign="top"><img
        src="../images/Adarrow.gif" border="0" height="16" width="16"
        alt=""></td>
      <td><b><font face="arial,helvetica,geneva" size="-1">Maintenance
            Builds</font></b><br> <font size="-1"
        face="arial,helvetica,geneva"> Maintenance builds are
          produced periodically to incorporate fixes into an existing
          release. They are typically built from tagged plug-in and
          feature pojects in a maintenance branch of the Git repository
          (i.e. R3_7_maintenance). Maintenance builds are promoted to a
          minor or service release (i.e. R3.7 or R3.7.1) after
          development teams have deemed one to be stable following one
          or more test-fix pass cycles. </font></td>
    </tr>
    <tr>
      <td align="right" valign="top"><img
        src="../images/Adarrow.gif" border="0" height="16" width="16"
        alt=""></td>
      <td><b><font face="arial,helvetica,geneva" size="-1">Patch
            Builds</font></b><br> <font size="-1"
        face="arial,helvetica,geneva"> Patch builds are produced
          rarely, but occasionally, to incorporate important fixes into
          an existing release, or perhaps even new features. They are
          intended to apply to only one specific release with the fixes
          or features being included in the next release. </font></td>
    </tr>
  </table>
</body>
</html>
